Add `COMMIT_META_CONTAINER_CMD` constant
authorColin Walters <walters@verbum.org>
Thu, 3 Feb 2022 17:40:46 +0000 (12:40 -0500)
committerColin Walters <walters@verbum.org>
Fri, 6 May 2022 16:53:57 +0000 (12:53 -0400)
commit9250effa8f951cc2647cc06240e83aa65f3ef8b7
tree9879f8a8d7b53ea7412a48a752d6098d16c27347
parent19224a411af0c77f0855fd812b0c16d966129c63
Add `COMMIT_META_CONTAINER_CMD` constant

Today we hardcode `/bin/bash` in
https://github.com/coreos/coreos-assembler/blob/2088d24884771093101d95f915c921505128ef76/src/cmd-build#L405

But that breaks the concept of a bidirectional bridge between
container image and ostree commit because this little bit of
knowledge is encoded at the buildsystem side.

This metadata key is intended to be written into an ostree commit,
and then we will use it automatically in `container encapsulate`.

The "source of truth" for this key will hence be able live in the same
place that's generating the ostree commit.

The more "proper" place for this is probably alongside the other
constants in the libostree core C code.  But that's tedious and
slow to release.  And Rust is the future.  And we've been slowly
adding more "core ostree" functionality here.
rust-bindings/rust/src/constants.rs [new file with mode: 0644]
rust-bindings/rust/src/lib.rs